Overview: Detect Inactivity
Use this operation to detect fields that have become inactive. Inactive fields are identified when the values don’t change for a specified period - this period can be either timestamp or row based. This operation will then mark the values that fall outside the period as bad quality and will assign a null value.
To use this operation effectively, you need in-depth knowledge of the process and the limits of inactivity that are acceptable.
Properties
Category: |
Modify |
Performance risk: |
High potential performance risk. The performance is influenced by the size of the text file being imported, which is determined by number of rows and/or the number of columns of the dataset. |
Knowledge required: |
Working knowledge of the software. |
Effect on datasets
How many datasets are required to perform this operation? |
One |
Does it create a new dataset? |
No |
Can you reconfigure this operation? |
Yes |
Can you apply this operation to a locked dataset? |
No |
Does it modify the current dataset in any way? |
Yes |
Requirements
-
For row based inactivity detection, a row number column is required.
-
For time based inactivity detection, a timestamp column is required.
Results
-
Values which are considered inactive will be replaced by NULL and will thus be deemed as bad quality.
-
The null values will be created PER FIELD, not across rows and therefore affecting all fields.
Related topics: